home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Tools (InfoMagic)
/
Internet Tools.iso
/
dos_win
/
winsock
/
maillist
/
94-05.Z
/
94-05
/
000166_news@bigblue.oit.unc.edu_Thu May 12 20:36:42 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-05-31
|
12KB
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA12391; Thu, 12 May 1994 17:15:19 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
id AA21077; Thu, 12 May 1994 17:14:02 -0400
Received: from GATEWAY by bigblue with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
To: winsock@sunsite.unc.edu
Date: Thu, 12 May 1994 20:36:42 GMT
From: rnichols@ih4ehw.ih.att.com (na8520d00-Nichols)
Message-Id: <CppIL6.vK@nntpa.cb.att.com>
Organization: AT&T Bell Laboratories
Sender: ses
References: <2qrdb3$lr@bmerha64.bnr.ca>, <1994May12.155317.3383@megatek.com>, <arnsteinCppEAr.L72@netcom.com>
Reply-To: rnichols@ihlpm.ih.att.com
Subject: Re: 32 bit access with SCSI no available. Hunh? was Re: Win Mosaic alpha 4 (my fix)
In article <arnsteinCppEAr.L72@netcom.com>,
>You've discovered the annoying fact that under Windows 3.1 and WFWG 3.11, SCSI
>disk I/O is SLOW, SLOW, SLOW. This is because Windows 3.1 won't do 32-bit
>disk access for (almost all) SCSI host adapters.
>
>As a result, each time SCSI I/O occurs, Windows must switch from 32-bit
>protected mode to real mode, and run code out of your SCSI host adapters ROM
>BIOS. Doubly slow!
>
>If you had 32-bit disk access going, Windows would run the code (32-bit disk
>access driver) in protected mode, without touching your SCSI BIOS.
>
>Only Future Domain host adapters are supplied with a driver that permits
>32-bit disk access from Windows. This driver does not work with WFWG 3.11 and
>besides, if you do use this driver, you may have to disable 32-bit disk access
>for your IDE drive(s).
>
>Windows 3.1 users:
>
> *** J U S T S A Y N O T O S C S I ***
You keep repeating this litany over and over, perhaps expecting it to
become true by repetition alone.
Windows can run just fine on SCSI system, and the presence or absence
of 32-bit access has little effect on the performance. I run Windows
on a SCSI system with no performance problems whatsoever.
If you are accessing your SCSI disk via the SCSI BIOS, though, you may
indeed have a major performance problem. For a busmastering SCSI
adapter, this implies that you are using the double-buffering function
of SMARTDrive, which will turn the fastest system into a dog. (This
was the case on my own system, as the manufacturer configured it.)
What you desperately need is an ASPI driver that either (a) supports
the virtual DMA interface directly, or (b) provides the necessary
buffering itself. This will allow you to get rid of the SMARTDRV
/DOUBLE_BUFFER line in your CONFIG.SYS. Furthermore, the SCSI BIOS is
no longer used once the ASPI driver is installed. This eliminates
another performance bottleneck since it is often impossible to enable
shadowing for the SCSI BIOS, forcing the CPU to run directly from the
8-bit EPROM. (In busmastering controllers, a portion of this address
range is used as a mailbox and must be writable. Most motherboards do
not allow you to shadow a range of addresses and still be able to
perform writes there.)
If you cannot obtain a driver that will permit you to eliminate
SMARTDrive's double buffering, then I would have to agree with your
"JUST SAY NO" advice -- for that particular SCSI adapter, anyway.
(BTW, to the best of my knowledge, the ASPI drivers in the
CorelSCSI! package do NOT allow you to eliminate SMARTDrive's double
buffering. Adaptec's ASPI4DOS has a switch to provide the necessary
buffering itself, as do the drivers for DTC's busmastering SCSI
adapters. For the Buslogic BT747S, the drivers perform the necessary
functions automatically, with no explicit switch required. I have no
experience with other SCSI adapters.)
--
Bob Nichols
AT&T Bell Laboratories
rnichols@ihlpm.ih.att.com
From tcemail!is3.indy.tce.com!FisherM@uunet.uu.net Thu May 12 09:30:00 1994
Received: from relay3.UU.NET by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA13652; Thu, 12 May 1994 17:33:43 -0400
Received: from uucp3.uu.net by relay3.UU.NET with SMTP
(5.61/UUNET-internet-primary) id AA03189; Thu, 12 May 94 17:33:43 -0400
Received: from tcemail.UUCP by uucp3.uu.net with UUCP/RMAIL
; Thu, 12 May 1994 17:33:42 -0400
Reply-To: tcemail!FisherM@is3.indy.tce.com
Received: from MSMAIL.INDY.TCE.COM (157.254.98.63) by nipper.indy.tce.com (PMDF
#12222) id <01HC9B8MAV4W8X1831@nipper.indy.tce.com>; Thu, 12 May 1994 16:32 EST
Received: by MSMAIL.INDY.TCE.COM with Microsoft Mail id
<2DD2BB19@MSMAIL.INDY.TCE.COM>; Thu, 12 May 94 16:26:17 PDT
Date: Thu, 12 May 94 16:30:00 PDT
From: Fisher Mark <FisherM@is3.indy.tce.com>
Subject: RE: Error 10037
To: WinSock <winsock@sunsite.unc.edu>
Message-Id: <2DD2BB19@MSMAIL.INDY.TCE.COM>
Encoding: 17 TEXT
X-Mailer: Microsoft Mail V3.0
Craig Larsen wrote in <larsenc.81.000B4811@lcs.com>:
> I'm running Chameleon v4.004. I have been consistently getting
>Error 10037 for the past few days.
>...
>BTW, my machine is a 486-33, 8MB RAM, 14.4k SL/IP connection.
10037 is the error code for when an attempt is made to perform a second
operation on a non-blocking socket while the first one is still in progress.
Did this error just start when you started using v4.004? I have been using
v4.00 without problems on an Ethernet connection.
======================================================================
Mark Fisher Thomson Consumer Electronics
fisherm@tcemail.indy.tce.com Indianapolis, IN
"Just as you should not underestimate the bandwidth of a station wagon
traveling 65 mph filled with 8mm tapes, you should not overestimate
the bandwidth of FTP by mail."
From news@bigblue.oit.unc.edu Mon May 12 18:41:16 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA14272; Thu, 12 May 1994 17:45:13 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
id AA28328; Thu, 12 May 1994 17:30:45 -0400
Received: from GATEWAY by bigblue with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
To: winsock@sunsite.unc.edu
Date: 12 May 1994 18:41:16 GMT
From: mbc@po.CWRU.Edu (Michael B. Comet)
Message-Id: <2qtt8c$srt@usenet.INS.CWRU.Edu>
Organization: Case Western Reserve University, Cleveland, OH (USA)
Sender: ses
Reply-To: mbc@po.CWRU.Edu (Michael B. Comet)
Subject: WSAAsyncSelct() - iMsg = what?
Question:
For asynch notification on a socket:
The application will get notified on hWnd passed in for the message
iMsg. wParam=socket id and lParam=event and error.
Question is, how do you select a good number/id for iMsg?
ie: How do I know my #define for my Msg won't conflict with say the
value of WM_PAINT etc...?
I would have assumed the message would be WM_COMMAND all the time,
and wParam would be used more like the msg id for menu items etc...
Can anyone explain this to me?
Thanks!
Mike Comet
mbc@po.cwru.edu
--
+--------------------------------------------------------------------------+
| Michael Comet, mbc@po.CWRU.Edu - CWRU, Software Engineer/Graphics Artist |
| Computer Graphics/Animation! - Liquid Vision SIG (go liquid), Freenet |
+--------------------------------------------------------------------------+
From news@bigblue.oit.unc.edu Thu May 12 13:43:29 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA14300; Thu, 12 May 1994 17:45:37 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
id AA34282; Thu, 12 May 1994 17:38:39 -0400
Received: from GATEWAY by bigblue with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
To: winsock@sunsite.unc.edu
Date: Thu, 12 May 1994 13:43:29 GMT
From: calanan@fstrf.org (Michael C. Calanan)
Message-Id: <calanan.11.000EBA00@fstrf.org>
Organization: Frontier Science
Sender: ses
Subject: Trumpet News Reader error "211 14..."?
I am having a problem With Trumpet News Reader for WS, Version 1.0A and am
wondering if anyone is having the same or can help.
I am running Trumpet Winsock 1.0A (Peter Tattam) over Windows for Workgroups
Version 3.10 that is running with the WIN32S.ZIP 32-bit DLL's that came with
an MPEG player: MPEGPLAY by Michael Simmons.
Every once in a while (maybe once per day to two days) I receive the following
error in a dialog box with only an OK button:
Trumpet Error:
211 14 882 895 {news.group.name}
It has happened with more than one group.
For info, I read and post via NNTP services @ news.fu-berlin.de (130.133.4.250)
Once this message comes up the machine locks up...Any one run into this?
Any Ideas?
Thanks in advance ...
Mike Calanan
calanan@fstrf.org
From ueen@sunyit.edu Thu May 12 14:09:19 1994
Received: from sunyit.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA15739; Thu, 12 May 1994 18:12:05 -0400
Received: by sunyit.edu (5.57/3.1.091691-SUNY -- Inst. of Tech.)
id AA23090; Thu, 12 May 94 18:09:20 -0400
Message-Id: <9405122209.AA23090@sunyit.edu>
From: ueen@sunyit.edu (Eugene E. Ninestein)
Date: Thu, 12 May 1994 18:09:19 -0400
X-Mailer: Mail User's Shell (7.2.3 5/22/91)
To: winsock@sunsite.unc.edu
Subject: PowerTCP
Dear Sirs/Ma'ams,
Have you heard of a product called PowerTCP?
Is it a shareware prod. or commercial?
Thanks
G.N.
--
From news@bigblue.oit.unc.edu Fri May 13 00:09:44 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA15921; Thu, 12 May 1994 18:15:07 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
id AA10222; Thu, 12 May 1994 18:14:19 -0400
Received: from GATEWAY by bigblue with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
To: winsock@sunsite.unc.edu
Date: Thu, 12 May 1994 14:09:44 +1000
From: c603905@showme.missouri.edu (Doug Nelson)
Message-Id: <c603905.19.00649775@showme.missouri.edu>
Organization: University of Missouri - Columbia
Sender: ses
Subject: killfiles and windows clients
sorry if this is the wrong area for this, but i use wintrumpet and winvn
exclusively so i've been isolated from the unix prompt and i thought someone
her might be more appropriate to help
how do you generate a killfile for windows readers? especially wintrumpet
tangent: wintrumpet and trumpet winsock are shareware, but i see nothing
about the fees involved anywhere (i looked) any info?
feel free to email direct if these are just too stupid or inappropriate for
the newsgroup
******************************************************
Doug Nelson c603905@showme.missouri.edu
the most feared woman in the universe?
-Tonya Rodham Bobbit ...of BORG!
From news@bigblue.oit.unc.edu Thu May 12 05:12:57 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA17532; Thu, 12 May 1994 18:45:07 -0400
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
id AA14113; Thu, 12 May 1994 18:22:08 -0400
Received: from GATEWAY by bigblue with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
To: winsock@sunsite.unc.edu
Date: Thu, 12 May 94 12:12:57 -0700 (PDT)
From: KCARPENT@mindlink.bc.ca (Ken Carpenter)
Message-Id: <44574@mindlink.bc.ca>
Organization: MIND LINK! - British Columbia, Canada
Sender: ses
Subject: WinSock 1.2 or 2.0 API?
Is there any word yet on when the next version of the WinSock Specification
will be released?
I am researching Windows Sockets for an embedded application and would like
to work with the latest version of the specification if it is available or
will be available soon.
Thanks,
Ken Carpenter